Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

@matwolff said in Mango RestApi Login V3.3.1: thanks for this as well. This would be an awesome option but would need something longer than a 3 month expiry as we wouldn't be able to trust our end users to update this regularly. You should be able to select a period longer than 3 months. You can also manually set the expiration date to anything you want. Just click the date input. [image: inHvnx4.png] @matwolff said in Mango RestApi Login V3.3.1: Also, I just tried to create a token to check it out and received an error with no token generated. Cannot deserialize value of type java.util.Date from String "2018-06-04T21:55:32.087Z": not a valid representation (error: Failed to parse Date value '2018-06-04T21:55:32.087Z': Unparseable date: "2018-06-04T21:55:32.087Z") I think you must have rest.customDateInputFormat set to something in your ${MA_HOME}/overrides/properties/env.properties file. Delete that line and also rest.customDateOutputFormat. They now have defaults for parsing/formatting dates as ISO 8601.

You're both absolutely right, maybe I wasn't refreshing the page to see the newly created events, I can now... Thanks so much for all of your help! :)

For anyone reading this thread, if you use Mango v3.3 you can now generate JWT authentication tokens from the users page on the new UI and use these to authenticate instead of logging in from your script. You do not need to use any CSRF/XSRF protection cookies/headers when using JWT authentication. Just set the one header on every request - Authorization: Bearer <token>